This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
RE: No, this is not about save conflicts! Please give your opinion here, Andre. ~Naomi Deskroterakol 11.Oct.03 06:21 PM a Web browser Applications Development 6.0.2 CF2Windows 2000
I think it's possible that when transaction logging is used, Notes is
fetching all the documents when you do the query that creates the collection,
and holding them all in memory until you ask for them.
If that's the case, then that's the bug. Nowhere in any documentation nor in
any historic behavior of Notes does this sort of quasi-caching take place. It
would be stupid to do so. In what transaction logging system anywhere at
anytime has "get me this record" meant "get me a version of this record as of
the start of this process?"
In other words, if the document is not "fetched" at the exact time of the
GetNextDocument call, then that's a bug -- plain and simple. If Lotus wishes
to introduce a .GetNextDocumentCached call, then that can appropriately be a
new method to the collection object.
Return to top
. . . . . . . . RE: No, this is not about save conf... (~Naomi Deskrote... 11.Oct.03) 
Print this page
